components/drift/actions/create-contact/create-contact.mjs (3)

53-61: Consider performance implications of object spreading with large customAttributes

The use of ...customAttributes could lead to performance issues if the customAttributes object is very large. Also, be careful when spreading user-provided objects as they might contain properties that could override your predefined attributes.

 const attributes = removeNullEntries({
   email,
   name,
   phone,
   source,
-  ...customAttributes,
+  ...(customAttributes || {}),
 });

---

63-72: Fix extra space in error message

There's an extra space between Error and the opening backtick in the error message.

 if (existingContact && existingContact.data.length > 0) {
-  throw new Error (`Contact ${email} already exists`);
+  throw new Error(`Contact ${email} already exists`);
 };

---

74-85: Improve formatting of warning messages in summary

The warning message concatenation could be formatted more clearly. If there are no warnings, the current implementation will still add a newline character.

- $.export("$summary", `Contact ${email} created.` + warnings.join("\n- "));
+ $.export("$summary", `Contact ${email} created.${warnings.length ? '\n- ' + warnings.join("\n- ") : ''}`);

components/drift/sources/new-lead-instance.mjs/new-lead-instance.mjs (2)

30-30: Fix spacing and improve comment clarity

There's an extra space before the assignment operator, and the comment could be more descriptive.

-    body.data.attributes =  result.data.attributes; //inject more data
+    body.data.attributes = result.data.attributes; // Enrich webhook data with full contact attributes

---

32-36: Consider adding validation for required fields

The code assumes that body.data.endUserId and body.timeStamp will always be present. Consider adding validation to handle cases where these fields might be missing.

+    const id = body.data?.endUserId || `lead-${Date.now()}`;
+    const ts = body.timeStamp || Date.now();
+
     this.$emit(body, {
       summary: `Contact "${email}" ID "${contactId}" updated`,
-      id: body.data.endUserId,
-      ts: body.timeStamp,
+      id,
+      ts,
     });

components/drift/sources/new-message-instant/new-message-instant.mjs (1)

12-17: Add validation for the conversationId prop.

The conversationId is defined as an integer type, but there's no validation to ensure it's a positive number.

Add validation for the conversationId in the run method:

  async run(event) {

    const { body } = event;
    const { drift } = this;

    const warnings = [];

+   if (this.conversationId && (isNaN(this.conversationId) || this.conversationId <= 0)) {
+     warnings.push("Conversation ID must be a positive number");
+   }

    if (this.emailOrId) warnings.push(...drift.checkEmailOrId(this.emailOrId));
    if (warnings.length > 0) console.log(warnings.join("\n- "));

components/drift/actions/get-contact/get-contact.mjs (1)

34-35: Improve the warning message formatting.

The warning messages are joined without a separator, which could make them harder to read.

-    $.export("$summary", `Contact ${contact.attributes.email} ID "${contact.id}"`
-      + " fetched successfully." +  warnings.join("\n- "));
+    $.export("$summary", `Contact ${contact.attributes.email} ID "${contact.id}" fetched successfully.` + 
+      (warnings.length ? "\n- " + warnings.join("\n- ") : ""));

components/drift/sources/new-contact-update/new-contact-update.mjs (2)

24-26: Use consistent object reference pattern.

You're using this.drift while other files use drift directly. Stay consistent with accessing the drift object.

-    const result = await this.drift.getContactById({
+    const result = await drift.getContactById({
       contactId,
     });

---

32-35: Remove redundant console.log statement.

There are two consecutive console.log statements with similar content.

-    console.log(body);
-
-    console.log("Contact updated webhook payload:", body);
+    console.log("Contact updated webhook payload:", body);

components/drift/actions/update-contact/update-contact.mjs (2)

8-8: Use consistent version numbering across components.

This component uses version "0.0.9" while other new components use "0.0.1". Maintain consistent versioning for new components.

-  version: "0.0.9",
+  version: "0.0.1",

---

86-86: Improve warning message formatting.

The warning messages are joined without proper formatting, which could make them harder to read.

-    $.export("$summary", `Contact ID ${contactId} updated successfully.` + warnings.join("\n- "));
+    $.export("$summary", `Contact ID ${contactId} updated successfully.` + 
+      (warnings.length ? "\n- " + warnings.join("\n- ") : ""));

components/drift/actions/delete-contact/delete-contact.mjs (2)

28-32: Handle array vs. object response explicitly for clarity

contact = contact.data[0] || contact.data; works, but the implicit truthy check obscures intent and could mask edge–cases (e.g. when data is an empty array). Prefer an explicit test so future readers immediately see why the fallback exists and to avoid accidentally operating on undefined.

-let contact = await drift.getContactByEmailOrId($, emailOrId);
-contact = contact.data[0] || contact.data;
+const res = await drift.getContactByEmailOrId($, emailOrId);
+const contact = Array.isArray(res.data) ? res.data[0] : res.data;
+
+if (!contact) {
+  throw new Error(`No contact returned for "${emailOrId}"`);
+}

---

39-41: Avoid dangling bullet when no warnings are present

warnings.join("\n- ") always appends a newline + dash, so the summary becomes
…deleted successfully.- when warnings is empty. Build the string conditionally:

-$.export("$summary", `Contact ${contactEmail} ID "${contactId}" deleted successfully.` +
-   warnings.join("\n- "));
+const summary = `Contact ${contactEmail} ID "${contactId}" deleted successfully.`
+  + (warnings.length ? `\n- ${warnings.join("\n- ")}` : "");
+$.export("$summary", summary);

components/drift/drift.app.mjs (2)

108-114: Remove unreachable else semicolon and streamline error path

Biome flags line 113 as unreachable because both branches throw. The trailing semicolon after the } is unnecessary and may confuse linters.

-        } catch (error) {
-          if (error.status === 404) {
-            throw new Error(`No contact found with ID: ${contactId}`);
-          } else {
-            throw error;
-          };
-        }
+        } catch (error) {
+          if (error.status === 404) {
+            throw new Error(`No contact found with ID: ${contactId}`);
+          }
+          throw error;
+        }

🧰 Tools

🪛 Biome (1.9.4)

[error] 113-113: This code is unreachable

... because either this statement ...

... or this statement will throw an exception beforehand

(lint/correctness/noUnreachable)

---

132-136: Typo in variable name & potential off-by-one

const firtsNew → firstNew. Small typo hinders readability.

Also, throwing when the id is not found may abort an otherwise recoverable poll. Consider logging and returning an empty list instead.

-const firtsNew = arr.indexOf(lastKnown);
-if (firtsNew === -1) throw new Error("Id not found");
-const newest = arr.slice(0, firtsNew);
+const firstNew = arr.indexOf(lastKnown);
+if (firstNew === -1) return [];
+const newest = arr.slice(0, firstNew);

components/drift/sources/new-conversation-instant/new-conversation-instant.mjs (2)

41-43: Debug statement left in source

console.log("here"); looks like leftover debugging noise and will spam logs.

-      console.log("here");

---

100-101: Event summary references contactId, not the conversation ID

For clarity to users looking at the event feed, consider using the conversation id (matches id field) or include both.

-summary: `New conversation with ID ${conversations[i].contactId}`,
+summary: `New conversation ${conversations[i].id} with contact ${conversations[i].contactId}`,

components/drift/common/methods.mjs (14)

12-15: Fix semicolon placement in conditional block.

There's an unnecessary semicolon after the conditional block which doesn't follow JavaScript best practices.

  isEmptyString(input) {
    if (this.isString(input)) {
      if (input.trim() === "") return true;
-    };
+    }

    return false;
  },

---

35-38: Fix semicolon placement in for loop.

There's an unnecessary semicolon after the for loop which doesn't follow JavaScript best practices.

    for (let i = 0; i < input.length; i++) {
      if (!this.isString(input[i]))
        return false;
-    };
+    }

---

62-65: Fix JSDoc comment formatting.

The comment has inconsistent slashes. The closing delimiter should match the opening style.

  /* =============================================================================================
  Function tries to parse the input as JSON,
  If it is not return the value as it was passed
- //==============================================================================================*/
+ ==============================================================================================*/

---

92-95: Fix semicolon placement after conditional block.

There's an unnecessary semicolon after the conditional block which doesn't follow JavaScript best practices.

    if (!this.isString(input)) {
      warnings.push("URL is not a string");
-
-    };
+    }

---

97-100: Fix semicolon placement after conditional block.

There's an unnecessary semicolon after the conditional block which doesn't follow JavaScript best practices.

    if (this.isEmptyString(input)) {
      warnings.push("URL is empty string");
      return warnings;
-    };
+    }

---

104-109: Fix semicolon placement and improve regex check.

There's an unnecessary semicolon after the conditional block, and the regex test could be improved.

    // Reject if spaces, tabs, or newlines are present
-    if ((/[ \t\n]/.test(trimmedInput))) {
+    if (/[ \t\n]/.test(trimmedInput)) {
      warnings.push( "Url contains invalid characters like space, backslash etc., please check." +
      this._reasonMsg(input));
      return warnings;
-    };
+    }

---

119-121: Fix semicolon placement after conditional block.

There's an unnecessary semicolon after the conditional block which doesn't follow JavaScript best practices.

    if (dubiousMatches) {
      warnings.push(" URL contains dubious or non-standard characters " + this._reasonMsg(input) );
-    };
+    }

---

130-135: Fix semicolon placement and improve warning message.

There's an unnecessary semicolon after the conditional block and the warning message could be better formatted.

      // Warn if user typed only one slash (e.g., https:/)
      if (/^(https?):\/(?!\/)/.test(input)) {
-
        warnings.push(` It looks like you're missing one slash after "${urlObject.protocol}".` +
        `Did you mean "${urlObject.protocol}//..."? ${this._reasonMsg(input)} `);
-
-      };
+      }

---

146-150: Fix semicolon placement after catch block.

There's an unnecessary semicolon after the catch block which doesn't follow JavaScript best practices.

      } catch (err) {
        warnings.push(" URL contains potentionally unacceptable characters\"" +
          this._reasonMsg(input));
-
-      };
+      }

---

147-148: Fix typo in warning message.

The warning message contains a typo in the word "potentially".

-        warnings.push(" URL contains potentionally unacceptable characters\"" +
+        warnings.push(" URL contains potentially unacceptable characters\"" +
          this._reasonMsg(input));

---

198-204: Consider using a more robust email validation regex.

The current regex is fairly minimal. While it checks basic structure, it might be worth considering a more comprehensive pattern that better matches email RFC standards.

For a more robust but still reasonable email validation, consider:

-    const basicPattern = /^[^@\s]+@[^@\s]+\.[^@\s]+$/;
+    // More comprehensive pattern checking for valid characters and structure
+    const basicPattern = /^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$/;

This pattern better enforces valid characters in the local and domain parts, and requires a minimum domain extension length.

---

255-274: Optimize the checkEmailOrId implementation.

Currently, we convert the input to a number twice. We can optimize this by storing the result of the first conversion.

  checkEmailOrId(input) {
    const warnings = [];
    const trimmed = this.trimIfString(input);
    
+    // Convert to number once
+    const numericValue = Number(trimmed);
    
    // If it's an ID like number or string (e.g 12345 or "12345");
    // it's Valid. Return empty warnings array.
-    if (this.isIdNumber(Number(trimmed))) return warnings;
+    if (this.isIdNumber(numericValue)) return warnings;

    // If it's not a string.
    if (!this.isString(trimmed)) {
      warnings.push("Provided value is not an email or ID-like value (e.g., 1234 or '1234').");
      return warnings;
    }

    warnings.push(...this.checkIfEmailValid(trimmed));
    return warnings;
  },

---

283-285: Improve error source determination.

The current method of determining the error source is somewhat simplified. Errors can come from other sources beyond API responses and internal code.

Consider a more detailed error classification:

-    const thrower = error?.response?.status
-      ? "API response"
-      : "Internal Code";
+    let thrower = "Internal Code";
+    
+    if (error?.response?.status) {
+      thrower = `API response (${error.response.status})`;
+    } else if (error?.code === 'ECONNREFUSED' || error?.code === 'ENOTFOUND') {
+      thrower = "Network connectivity";
+    } else if (error?.code === 'ETIMEDOUT') {
+      thrower = "Request timeout";
+    }

---

1-302: Overall good structure but consider adding common validation interfaces.

The utility module provides a comprehensive set of validation and helper functions. However, it would be beneficial to introduce some higher-level validation interfaces that combine multiple checks for common scenarios.

Consider adding a high-level validation method that combines related checks:

validateContactInput(input) {
  const warnings = [];
  
  // Check required fields
  if (!input.email && !input.id) {
    warnings.push("Either email or id must be provided for contact operations");
  }
  
  // Validate email if provided
  if (input.email) {
    warnings.push(...this.checkIfEmailValid(input.email));
  }
  
  // Validate id if provided
  if (input.id && !this.isIdNumber(Number(input.id))) {
    warnings.push("Contact ID must be a positive integer");
  }
  
  return warnings;
},

This would help standardize validation across different actions that operate on contacts.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

components/drift/drift.app.mjs (2)

45-46: Add fallback error handling for missing OAuth token

Similar to the issue in the _makeRequest method, the OAuth token should have appropriate error handling here.

- "Authorization": `Bearer ${this.$auth?.oauth_access_token}`,
+ "Authorization": `Bearer ${this.$auth?.oauth_access_token ?? (() => {
+   throw new Error("Drift OAuth access token is required");
+ })()}`,

---

32-34: 🛠️ Refactor suggestion

Add fallback error handling for missing OAuth token

The current implementation doesn't handle the case where this.$auth?.oauth_access_token is undefined. This could lead to silent failures with unclear error messages.

- "Authorization": `Bearer ${this.$auth?.oauth_access_token}`,
+ "Authorization": `Bearer ${this.$auth?.oauth_access_token ?? (() => {
+   throw new Error("Drift OAuth access token is required");
+ })()}`,

components/drift/drift.app.mjs (4)

40-48: Reduce duplication by leveraging existing _makeRequest method

The getNextPage method duplicates the authorization header logic that already exists in _makeRequest. This could lead to inconsistencies if authentication requirements change.

- getNextPage($, url) {
-   return axios($, {
-     method: "GET",
-     url,
-     headers: {
-       "Authorization": `Bearer ${this.$auth?.oauth_access_token}`,
-     },
-   });
- },
+ getNextPage($, url) {
+   return axios($, {
+     method: "GET",
+     url,
+     headers: {
+       "Authorization": `Bearer ${this.$auth?.oauth_access_token}`,
+     },
+   });
+ },

Alternatively, you could modify _makeRequest to accept a full URL instead of constructing it from base URL and path, then use it for both cases.

---

124-127: Remove unnecessary semicolon

For consistency with the rest of the codebase, remove the unnecessary semicolon after the closing brace.

  if (!response?.data?.length) {
    throw new Error(`No contact found with email: ${email}`);
-  };
+  }

---

133-134: Fix typo in variable name

The variable name "firtsNew" appears to be a typo for "firstNew".

- const firtsNew = arr.indexOf(lastKnown);
- if (firtsNew === -1) throw new Error("Id not found");
+ const firstNew = arr.indexOf(lastKnown);
+ if (firstNew === -1) throw new Error("Id not found");

---

8-138: Add JSDoc documentation for improved code readability

The methods in this file lack documentation. Adding JSDoc comments would improve code clarity and maintainability, especially for other developers who might need to work with this code in the future.

For example, add documentation to the getContactByEmailOrId method:

/**
 * Retrieves a contact by either email or ID
 * @param {Object} $ - Pipedream event object
 * @param {string|number} emailOrId - Either an email address or a contact ID
 * @returns {Promise<Object>} - The contact data
 * @throws {Error} If no contact is found or if there's an API error
 */
async getContactByEmailOrId($, emailOrId) {
  // Existing implementation
}

Consider adding similar documentation to all methods in this file.

🧰 Tools

🪛 Biome (1.9.4)

[error] 113-113: This code is unreachable

... because either this statement ...

... or this statement will throw an exception beforehand

(lint/correctness/noUnreachable)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

components/drift/sources/new-lead-instance/new-lead-instance.mjs (2)

3-12: Component setup looks good but consider adding webhook setup instructions

The component is well-structured with appropriate key, name, and description. The document link is helpful for reference.

However, since this is a webhook-based source, consider adding setup instructions either in the description or as a separate hooks section to guide users on how to configure the webhook in Drift.

---

32-36: Update the summary message for consistency

The summary message indicates an update ("Contact X updated"), but this component is designed to trigger when a new lead adds their email in chat (as stated in the description).

this.$emit(body, {
-  summary: `Contact "${email}" ID "${contactId}" updated`,
+  summary: `New lead identified: "${email}" (ID: "${contactId}")`,
  id: body.data.endUserId,
  ts: body.timeStamp,
});

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

components/drift/drift.app.mjs (2)

107-118: Remove unnecessary semicolons

There are unnecessary semicolons at the end of blocks that should be removed for consistency.

        if (!response?.data?.length) {
          throw new Error(`No contact found with email: ${email}`);
-        };
-      };
+        }
+      }

---

123-128: Fix typo in variable name

There's a typo in the variable name at line 124 - firtsNew should be firstNew.

-      const firtsNew = arr.indexOf(lastKnown);
+      const firstNew = arr.indexOf(lastKnown);
       if (firtsNew === -1) throw new Error("Id not found");
-      const newest = arr.slice(0, firtsNew);
+      const newest = arr.slice(0, firstNew);
       return newest.reverse();

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

components/drift/sources/new-lead/new-lead.mjs (1)

23-23: Fix typo in summary message.

There's a spelling error in the summary text.

-      summary: `New lead. Contact ID "${body.id}" proveded their email`,
+      summary: `New lead. Contact ID "${body.id}" provided their email`,

components/drift/sources/new-conversation/new-conversation.mjs (1)

6-6: Fix typo in component description.

There's a spelling error in the description text.

-  description: "Emit new event when a new convesation is started in Drift. [See the documentation](https://devdocs.drift.com/docs/webhook-events-1).",
+  description: "Emit new event when a new conversation is started in Drift. [See the documentation](https://devdocs.drift.com/docs/webhook-events-1).",

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

components/drift/common/utils.mjs (1)

1-23: Typo and performance issues already identified

The previous review correctly identified the typo in isNotEmpyString and the O(n²) performance issue with spread operator in the reducer.

🧰 Tools

🪛 Biome (1.9.4)

[error] 19-19: Avoid the use of spread (...) syntax on accumulators.

Spread syntax should be avoided on accumulators (like those in .reduce) because it causes a time complexity of O(n^2).
Consider methods such as .splice or .push instead.

(lint/performance/noAccumulatingSpread)

components/drift/sources/new-message/new-message.mjs (1)

44-48: Error handling for API calls already identified

The previous review correctly identified the need for error handling around the drift API calls.

components/drift/drift.app.mjs (1)

117-117: Remove unnecessary semicolon

The previous review already identified this issue.

components/drift/common/utils.mjs (1)

28-28: Remove extra space before parenthesis for consistency

-    throw new Error ("Message context is not an object");
+    throw new Error("Message context is not an object");

components/drift/sources/new-message/new-message.mjs (1)

46-46: Remove debug console.log statement

This appears to be debug code that should be removed before production.

-    console.log(messageContext);

components/drift/sources/new-conversation/new-conversation.mjs (3)

7-7: Fix grammatical error in description

-  description: "Emit new when a new conversation is started in Drift. [See the documentations](https://devdocs.drift.com/docs/retrieve-a-conversation)",
+  description: "Emit new event when a new conversation is started in Drift. [See the documentation](https://devdocs.drift.com/docs/retrieve-a-conversation)",

---

67-67: Remove extra space before parenthesis for consistency

-      throw new Error ("lastConversation not found in fetched data. Skipping emit.");
+      throw new Error("lastConversation not found in fetched data. Skipping emit.");

---

78-78: Clarify the summary message

The summary should be clearer about what ID is being referenced.

-        summary: `New conversation with ID ${conversations[i].contactId}`,
+        summary: `New conversation with contact ID ${conversations[i].contactId}`,

components/drift/drift.app.mjs (4)

24-24: Clean up comment artifacts

Remove the trailing comment artifacts.

-          "Authorization": `Bearer ${this.$auth?.oauth_access_token}`, //"Bearer iHlC8LmFQiTH0DcWds7ETMRMmo3BvUyP", // ,
+          "Authorization": `Bearer ${this.$auth?.oauth_access_token}`,

---

124-124: Fix typo in variable name

-      const firtsNew = arr.indexOf(lastKnown);
+      const firstNew = arr.indexOf(lastKnown);

---

125-125: Use consistent capitalization for "ID"

-      if (firtsNew === -1) throw new Error("Id not found");
+      if (firstNew === -1) throw new Error("ID not found");

---

126-126: Update variable reference after fixing typo

-      const newest = arr.slice(0, firtsNew);
+      const newest = arr.slice(0, firstNew);

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

components/drift/common/utils.mjs (3)

8-8: Fix typo in variable name.

The variable name has a typo that affects readability and consistency.

-    const isNotEmpyString = typeof value === "string" && value.trim() !== "";
+    const isNotEmptyString = typeof value === "string" && value.trim() !== "";

---

17-17: Fix typo in variable reference.

This references the same misspelled variable from line 8.

-        (isNotEmpyString || isNotEmptyArray || isNotEmptyObject || isBoolean || isNumber))
+        (isNotEmptyString || isNotEmptyArray || isNotEmptyObject || isBoolean || isNumber))

---

19-21: Optimize performance by avoiding spread operator in reducer.

Using the spread operator in a reducer causes O(n²) time complexity, which is inefficient for large objects. This was flagged by static analysis tools.

-      ? {
-        ...acc,
-        [key]: value,
-      }
+      ? Object.assign(acc || {}, { [key]: value })
       : acc;

🧰 Tools

🪛 Biome (1.9.4)

[error] 19-19: Avoid the use of spread (...) syntax on accumulators.

Spread syntax should be avoided on accumulators (like those in .reduce) because it causes a time complexity of O(n^2).
Consider methods such as .splice or .push instead.

(lint/performance/noAccumulatingSpread)

components/drift/drift.app.mjs (1)

117-118: Remove unnecessary semicolons after closing braces.

These semicolons create unreachable code and violate JavaScript syntax conventions.

        if (!response?.data?.length) {
          throw new Error(`No contact found with email: ${email}`);
-        };
-      };
+        }
+      }

components/drift/common/utils.mjs (1)

28-29: Fix formatting and unnecessary semicolon.

Remove the space before the semicolon and the unnecessary semicolon after the if statement closing brace.

-    throw new Error ("Message context is not an object");
-  };
+    throw new Error("Message context is not an object");
+  }

components/drift/drift.app.mjs (1)

124-124: Fix typo in variable name.

The variable name has a typo that affects code readability.

-      const firtsNew = arr.indexOf(lastKnown);
+      const firstNew = arr.indexOf(lastKnown);

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

components/drift/common/utils.mjs (2)

8-8: Fix typo in variable name

The variable name has a typo: isNotEmpyString should be isNotEmptyString.

Also applies to: 17-17

---

19-19: Avoid spread operator in reduce accumulator for performance

Using the spread operator in a reduce accumulator causes O(n²) time complexity. Consider using Object.assign or direct property assignment instead.

🧰 Tools

🪛 Biome (1.9.4)

[error] 19-19: Avoid the use of spread (...) syntax on accumulators.

Spread syntax should be avoided on accumulators (like those in .reduce) because it causes a time complexity of O(n^2).
Consider methods such as .splice or .push instead.

(lint/performance/noAccumulatingSpread)

components/drift/common/utils.mjs (1)

28-29: Consider more descriptive error message

The error message could be more specific about what constitutes a valid message context.

-    throw new Error ("Message context is not an object");
+    throw new Error("Message context must be a non-null object (not an array)");

components/drift/drift.app.mjs (2)

31-39: Consider consolidating pagination logic

The getNextPage method duplicates header logic from _makeRequest. Consider using _makeRequest for consistency.

 getNextPage($, url) {
-  return axios($, {
-    method: "GET",
-    url,
-    headers: {
-      "Authorization": `Bearer ${this.$auth?.oauth_access_token}`,
-    },
-  });
+  return axios($, {
+    method: "GET",
+    url,
+    headers: {
+      "Authorization": `Bearer ${this.$auth?.oauth_access_token}`,
+    },
+  });
 },

---

117-118: Remove unnecessary semicolons

Unnecessary semicolons after closing braces should be removed for cleaner code.

         if (!response?.data?.length) {
           throw new Error(`No contact found with email: ${email}`);
-        };
-      };
+        }
+      }

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro